Update to work with latest DecapCMS and minor feature tweaks #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
I went back and checked what my original problem was, and if I build this module using the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to use this module with the latest version of DecapCMS, which depends on React 19. I could not get the build to work, and would get strange React errors when deploying the module, so I followed the example of https://github.com/iamspark1e/decap-cms-widget-starter and switched to Vite. I also added a configuration option to make the ability to regenerate the ID an optional thing rather than always being available.
If you'd rather not switch to Vite I can try to get Webpack working, but I may need some assistance in that case. Sorry about that!